Connected Helmet System And Method Of Operating The Same

ABSTRACT

A system for controlling a vehicle includes a programming device comprising an application for programming vehicle function settings of a vehicle. The programming device has a transmitter communicating the vehicle function settings of the vehicle. A vehicle receiver is disposed within the vehicle. The vehicle receiver receives the vehicle function settings. A vehicle is controller disposed within the vehicle. A helmet generates a helmet movement signal in response to sensing movement of the helmet. The helmet communicates a helmet identifier to the vehicle controller through the receiver in response to the helmet movement signal. The vehicle controller controls a vehicle function in response to the vehicle function settings.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/668,980 filed on Oct. 30, 2019, which claims the benefit of U.S.Provisional Application No. 62/754,116, filed on Nov. 1, 2018. Theentire disclosures of the above applications are incorporated herein byreference.

FIELD

The present disclosure relates to a helmet for use with a vehicle and,more particularly, to a helmet that allows function settings to becommunicated to a vehicle operating system.

BACKGROUND

This section provides background information related to the presentdisclosure which is not necessarily prior art.

All-terrain vehicles, snowmobiles and other types of off road vehiclesmay be used by adults and children alike. Certain vehicles allow theuser to adjust settings through menu displays at the vehicle. However,multiple users may use a vehicle and thus a user's favorite settingsmust be adjusted if another user changes them.

Because various types of off road vehicles are also used by children,parents may wish to restrict the operation of various functions of thevehicles. However, no known way to restrict such functions is known.

SUMMARY

This section provides a general summary of the disclosures, and is not acomprehensive disclosure of its full scope or all of its features.

The present disclosure provides a system for adjusting operationfunctions of a vehicle to be set and adjusted as the driver operates orapproaches a vehicle from stored setting communicated from a helmet.

In one aspect of the disclosures a system comprises a controller and avehicle controller disposed within a vehicle. A helmet communicates anidentifier to the vehicle. The controller enables the vehicle to startin response to the identifier.

In another aspect of the disclosure, a helmet for communicating with avehicle function controller has a first memory, a first transmitter, afirst receiver and a first controller in communication with the firstmemory, the first transmitter and the first receiver. The first receiverreceives a plurality of vehicle function settings. The first memorystores the vehicle function settings within a memory of the helmet. Thefirst transmitter communicates the vehicle function settings from thefirst memory to the vehicle function controller.

In yet another aspect of the disclosure, a method includes receiving aplurality of vehicle function settings at a first receiver disposedwithin a helmet, storing the vehicle function settings within a firstmemory of the helmet, communicating the vehicle function settings to avehicle function controller using a first transmitter disposed withinthe helmet, receiving the vehicle function settings a second receiverassociated with a vehicle function controller, storing the vehiclefunction settings within a second memory associated with a vehiclefunction controller and controlling a vehicle function in response tothe vehicle function settings.

Further areas of applicability will become apparent from the descriptionprovided herein. The description and specific examples in this summaryare intended for purposes of illustration only and are not intended tolimit the scope of the present disclosure.

DRAWINGS

The drawings described herein are for illustrative purposes only ofselected examples and not all possible implementations, and are notintended to limit the scope of the present disclosure.

FIG. 1 is a perspective view of a vehicle setting system according tothe present disclosure.

FIG. 2 is block diagrammatic view of the function control systemaccording to the present disclosure.

FIG. 3 is a block diagrammatic view of a programming device according tothe present disclosure.

FIG. 4A is an initial helmet control application screen example.

FIG. 4B is a screen display for enabling or disabling various helmetsfor a system.

FIG. 4C is a helmet control screen display for initiating variousfunction settings.

FIG. 4D is a screen display for setting geographic boundaries.

FIG. 4E is a screen display for setting personal characteristics.

FIG. 5 is a block diagrammatic view of the helmet control systemaccording to the present disclosure.

FIG. 6 is a block diagrammatic view of a vehicle function controller.

FIG. 7 is a block diagrammatic view of a screen display for the vehiclefunction controller.

FIG. 8 is a flowchart of a method for setting the vehicle settings at anapplication for a programming device.

FIG. 9 is a flowchart of a method for operating a vehicle andcommunicating function settings from a helmet to a vehicle functioncontroller.

FIG. 10 is a flowchart of a method for operating using multiple helmets.

FIG. 11 is a method for initiating the pairing of a helmet to a vehicle.

FIG. 12 is a detailed flow chart of the method of pairing.

Corresponding reference numerals indicate corresponding parts throughoutthe several views of the drawings.

DETAILED DESCRIPTION

Example embodiments will now be described more fully with reference tothe accompanying drawings. Although the following description includesseveral examples of a motorcycle application, it is understood that thefeatures herein may be applied to any appropriate vehicle, such assnowmobiles, all-terrain vehicles, utility vehicles, moped, automobiles,scooters, etc. The examples disclosed below are not intended to beexhaustive or to limit the disclosure to the precise forms disclosed inthe following detailed description. Rather, the examples are chosen anddescribed so that others skilled in the art may utilize their teachings.

The present disclosure provides a system that uses a helmet andelectronics within the helmet to communicate function settings to acontroller of a vehicle. By providing and storing function settingswithin the helmet, the functions settings of the vehicle may be updatedand operated accordingly. The function settings are a type of data thatcorrespond to a range of desired operation for a particular function.The function setting may set a maximum or minimum for a function (e.g.,speed, radio volume). The function settings may set a geographicalboundary or desired presets (one or more data values) for a function(e.g., radio setting, suspension pre-height).

Referring now to FIG. 1, a vehicle 10 such as a utility vehicle isillustrated having wheels 12 and a body 14 that houses a vehiclefunction controller 16. The vehicle function controller 16 is incommunication with a helmet 20. The helmet 20 includes a helmet controlsystem 22. A programming device 30 includes an application 32 used forprogramming limits for the functions of the vehicle 10 and communicatingthe data corresponding thereto to the helmet control system 22.

Referring now to FIG. 2, a block diagrammatic view of the vehiclefunction control system 50 of vehicle 10 is illustrated having a vehiclefunction controller 16. The vehicle function controller 16 is incommunication with the helmet control system 22 of the helmet 20. Theprogramming device 30 has an application 32 for communicating or causingthe programming device to communicate with the helmet control system 22.The programming device 30 may enable or disable a helmet frominteracting with the vehicle function controller 16. Details of thecommunication functions are set forth in further detail below.

Referring now to FIG. 3, a programming device 30 is illustrated infurther detail. The programming device 30 may be a cellular phone, atablet, a computer or another type of device. The programming device 30includes a receiver 310 and a transmitter 312, both of which may beincluded within a transceiver 314. That is, the receiver 310 andtransmitter 312 may be formed on a single chip and may be referred to asthe transceiver 314. However, a separate receiver 310 and a separatetransmitter 312 may be provided within the programming device. Thereceiver 310 and the transmitter may use various types of technologiesincluding Bluetooth, Wi-Fi, short range or long range communications,cellular communications or the like for communicating with the helmetand the vehicle function controller. The programming device includes acontroller 320. The controller 320 may be a microcomputer or discreetcircuitry. The controller 320 is in communication with a memory 322 suchas a solid state device or a hard drive.

Controller 320 may also be in communication with a user interface 324.The user interface 324 is used for communicating signals to thecontroller 320. The user interface 324 may comprise a series of buttons,switches or dials and may include a keyboard. The user interface 324provides various types of signals for controlling the function settings.

A display 326 may also be in communication with the controller 320. Thedisplay 326 may be a touchscreen display which also acts as a userinterface. The display 326 displays various settings and queries formaking these settings. In conjunction with the user interface 324,various display items may be selected or adjusted as described in moredetail below. The controller 320 receives the selection signals from theuser interface 324 so that the control function settings are storedwithin the memory 322.

The controller 320 may include a limitation application 340 may be usedto generate the display and receive and communicate various menus sothat different types of function limitations may be selected. Thefunction limitations may take the form of data stored within the memory322.

Referring now to FIG. 4A, the limitation application 340 may manifestitself within a screen display 410. Screen display 410 may provide amethod for secure access to the application by requesting an identifierto be entered within the box 412. The identifier may be entered usingthe user interface 324 illustrated in FIG. 3. The display 410 itself maybe used if a touch screen display is provided.

Referring now to FIG. 4B, the system may use an enable box 414 or adisable box 416 to enable various helmets, two of which “A” and “B” areset forth.

Referring now to FIG. 4C, the helmet function settings controlapplication may provide a user interface 420 used for enabling variouslimitations for operating the vehicle. The use of application 340 maydisable function settings from the helmet. The limitation application340 illustrated in FIG. 3 may allow various controls to be preset forthe vehicle and ultimately store within the helmet. By setting thelimitations, parental controls may be provided. Further, adults may alsobenefit from this system by presetting various settings within thevehicle. In this example, the speed limit that may be set by a speedlimit selector 422. The speed limit selector 422 may be moved by buttonswithin the user interface 324 or by touching the screen display on atouchscreen display. All of the selectors set forth below may be changedby the user interface or by touching the touchscreen display dependingon the design of the system. The user interface 420 may be displayed ona screen display after the user has entered the user identifier toaccess the control app.

A volume selector 424 may also be provided. The volume selector 424 mayset a maximum allowed volume for the radio or audio output of thevehicle.

A ride height selector 426 may also be provided. The ride heightselector 426 may set the suspension preloads so that a predeterminedride height may be provided for the user. Different uses of the vehiclessuch as loading of the vehicle and different weights of the passengersmay deem desirable the change of a ride height according to a user'spreference.

A steering effort selector 428 may also be provided in the system. Thesteering effort selector 428 may change the amount of steering effortthat must be applied to the steering wheel in order to turn the steeringwheel.

A radio preset selector 430 may provide various numbers of preset radiostation frequencies that may be selected or changed. The preset selector430 may have individual selection control buttons 432A, 432B, 432C and432D. By touching one of the individual radio selector buttons 432A-D,the frequency of the radio may be preselected. In this example button432D is selected and arrows 434D and 432U are provided and correspond toan up frequency or down frequency selection. The frequency may bedisplayed within the selector button 432D or adjacent to the button 432.

A maps set selector 440 may also be provided within the user interface420. The maps set selector 440 may initiate a screen illustrated in FIG.4C. In FIG. 4D a screen display 450 is set forth with a map 452 and ageographical boundary 454 that may be moved by the user interface or bytouching the display. The boundary 454 may be changed so that thevehicle may be operated only within a certain geographical boundary.

Referring back to FIG. 4C, a send button 460 may also be provided. Thesend button 460 may allow the various settings to be communicated to thememory of the programming device 30. The send button 460 may also act tosend the functions settings to the transmitter 312 where they may betransmitted to the helmet control system of the helmet 20 of FIGS. 1 and2. A personal button 462 may also be included within the user interface420. The personal button, when selected, brings up the screen displayillustrated in the user interface 470 of FIG. 4E.

Referring now to FIG. 4E, a personal characteristics user interface 470is provided. In this example various personal characteristics for arider may be set. Menu selection 472 allows the operator to select theage. Menu selection 474 allows the operator to select the height of therider. Menu selection 476 allows the weight of the rider to be selected.The age, height and weight may all be numerically typed in. However,slide dials, buttons or other types of user interface may also be usedto select the appropriate age. Menu selection 478 may also allow theability of the rider to be set. A slide dial 480 may be used to set thelevel from expert to beginner for a particular rider. After the personalsettings are selected button 482 may be set the personal settings for aparticular user. The personal settings may be ultimately communicated toa helmet to be stored therein and ultimately communicated to a vehicle.

Referring now to FIG. 5, the helmet control system 22 is illustrated infurther detail. The helmet control system 22 includes a controller 510that is in communication with a memory 512. The memory 512 may be asolid state device. The controller 510 may also be coupled to a display514. The display 514 may be a simple indicator such as an LED ormultiple LEDs to communicate that various functions have been performed.A power supply 516 such as a battery may also be provided within thehelmet control system 22. The controller 510 may be coupled to a userinterface 520. The user interface 520 may be one or more buttons, arrowsor other types of selectors for controlling the function of thecontroller 510. For example, the user interface 520 may be used forchanging the helmet control system 22 to an active state where itreceives the function settings from the application.

The controller 510 is coupled to a receiver 530 and a transmitter 532.The receiver 530 and the transmitter 532 may be incorporated within atransceiver 534 as one unit. The receiver 530 may be used to receivesignals from the programming device either directly or through anetwork. The transmitter 532 may be used to transmit function settingsstored within the memory 512 to the vehicle function controller 16.

A movement sensor 536 is also in communication with the controller 510.The movement sensor 536 generates a movement signal that corresponds tothe movement of the helmet. The movement sensor 536 may be one of avarious number of different types of sensors including a piezoelectricsensor, an accelerometer, or the like. The movement sensor signal iscommunicated to the controller 510 and, as will be described in moredetail below, may initiate a pairing process between the helmet and thevehicle.

Referring now to FIG. 6, the vehicle function controller 16 isillustrated in further detail. The vehicle function controller 16 mayinclude a controller 610 that is in communication with a memory 612 forstoring various function settings therein. The controller 610 may be amicroprocessor, an integrated circuit or discrete circuit. The functionsettings may be saved until the function settings are changed bycommunicating with the helmet control system 22 of FIGS. 1, 2 and 5. Thecontroller 610 may be in communication with a display 614. The display614 may be used to display various RIDE COMMAND® functions for userselectability. The RIDE COMMAND® system may be used for the vehiclefunction controller. The RIDE COMMAND® system has various capabilitiesthat are enhanced by the present examples. The function settings may setmaximum or minimum settings for various types of functions. As long asthe selected functions are in between the display or the user interface616 may be used to adjust the various functions settings. The controller610 may also be in communication with a controller area network (CAN)interface 618. The controller area network interface 618 may be used tocommunicate signals to the various vehicle systems such as a suspensionsystem, steering system, a braking system or the like. The display 614may also provide indicators to warn the vehicle operator that they areattempting to operate outside the various parameters.

The vehicle function controller 16 may incorporate the functions of theprogramming device 30 and the application 32 therein. In this manner theprogramming device 30 may be integral to the function controller 16 andmay be displayed through the display 614. The RIDE COMMAND® system mayincorporate the application 32. Of course, the application 32 forchanging settings could be password protected to prevent unauthorizedchanges (e.g., parental controls).

A power supply 620 may be used to power the vehicle function controller.The power supply 620 may be a vehicle battery.

The controller 610 may also be in communication with a receiver 630 atransmitter 632 both of which may be incorporated into a transceiver634. The receiver may be used to receive the signal from the helmetcontrol system 22 when the helmet is proximate to the vehicle. Thesystem may be activated by a key or by a proximity sensor 640 which iscoupled to the controller 610. That is, the controller 610 may provide alow power beacon signal through the receiver 630 to sense the approachof a helmet control system 22 which in turn may generate a responsesignal that provides the function settings to the controller 610 andultimately that to be stored within the memory 612. The vehicle may belimited from starting or may get a low top speed. A proximity sensor 640may also generate a signal to recognize that the helmet is within in acertain proximity of the system. The proximity sensor 640 may, forexample, be a motion sensor to detect motion nearby the vehicle orwithin the passenger compartment of the vehicle to which in turnactivates the controller 610 to power the receiver 630 to receive thefunction settings. The proximity sensor 640 may be a key press or buttonpress to turn on the vehicle as well. This indicates that the vehicleoperator is within the vehicle and thus proximate to the proximitysensor 640.

A lockout module 642 may also be included in the vehicle functioncontroller. The lockout module 642 allows the vehicle to not startunless a properly authorized helmet is provided. The helmet communicatesan identifier to the vehicle function controller and thus the lockoutmay be disabled when a helmet is positioned close to the vehicle or inthe riding positon of the vehicle.

A global positioning system receiver (GPS) 650 communicates a globalposition to the controller 610. The global position signal from theglobal position system 650 corresponds to a coordinate position of thevehicle.

A pairing module 654 is coupled to a controller 610. The pairing module654 controls the pairing process of the helmet with the vehicleaccording to the method set forth below. In particular, the pairingmodule 654 together with various inputs from the vehicle controller andthe helmet allow the helmet and the vehicle to communicate through theirrespective transmitters/receivers. A timer 666 is used to time variousfunctions such as a time out function or a function such as keepingtrack of an amount of time since an ignition of the vehicle.

An ignition module 668 generates an ignition signal that corresponds toa starting or turning-on of the vehicle. The ignition module 668 may,for example, generate an ignition signal in response to a key rotatingin an ignition lock. The ignition module 668 may also be incommunication with a push button type system that generates an ignitionsignal in response to the push of a button. The timer 666 may be used totime a time since the ignition module 668 was activated and the ignitionsignal was generated.

Referring now to FIG. 7, the display 614 of the vehicle functioncontroller is set forth in one example. The display 614 may display orindicate various functions have been activated. In this example, ahelmet beacon enabled indicator 710 illustrates that the helmet beaconhas been communicated with by the vehicle function controller. Thehelmet battery level indicator 712 may indicate the battery level of thehelmet by word descriptors or by an indicator 714 that represents abattery being full or partially full. A status indicator 716 may be usedto indicate the status of various functions of the system. Anotification indicator 718 may indicate that a notification from thehelmet control system 22 is being received. A RIDE COMMAND® indicator720 may be used to indicate that the RIDE COMMAND® is limited by variousfunctions. A complete lockout of starting may be performed without anauthorized helmet. A speed limited indicator 722 may be activated orilluminated when the speed of the vehicle has reached the commandsetting. A radio volume limited indicator 724 may be illuminated oractivated when the radio volume is attempted to be set over the presetfunctions settings. An operation time limited indicator 726 may providean indicator that the amount of time or the time of day is beyond thetime of day for operation of the vehicle. A geographical indicator 728may indicate that the geographical boundary of the vehicle may have beenexceeded. This may be performed by the operation of the GPS 650 of thevehicle as set forth in FIG. 6.

The display 614 may act as a user interface as described above when thedisplay 614 is a touch screen display. A confirmation indicator 730 maybe illuminated to allow the vehicle operator to confirm the pairing ofthe vehicle and the helmet. The confirmation indicator 730 may displaywording such as “confirm pairing to XYZ helmet”. “XYZ” refers to anidentifier of the helmet. The identifier may be a name or otheralphanumeric identifier. When pairing is desired, the user operator mayselect the confirmation indicator 730 and the helmet and the vehiclewill be able to communicate various signals therebetween. Theconfirmation indicator 730 may continue to be illuminated, change thewording thereof or disappear after the helmet and the vehicle are pairedan intercommunicating.

Referring now to FIG. 8, a method for operating the system between theprogramming device 30 and the helmet 20 is set forth. In this example,the helmet control application is selected at the programming device instep 810. This may be selected by clicking on an icon, selecting an iconfrom a screen or interfacing with a user interface such as arrow keysand a select button. In step 812 an identifier identifying the user ofthe application may be set forth. The identifier may be entered once andsaved within the user device.

In step 814 a vehicle may be selected from a user interface. That is,multiple vehicles may be associated with a single user. In step 816 theuser may be selected. Multiple users may also be associated with aparticular account. For example, the owner of the vehicle may havedesired settings for kids and spouses as well as friends. In step 818,multiple helmets may also be associated in an account. In this step, thedesired helmet to be programmed may be selected. After step 820 adisable/enable function may be performed for the helmet or user. Ifdisable is selected, the previously stored functions of the helmet maybe deleted. In step 820 if enable is selected step 824 is performed. Instep 824 the user interface illustrated above with respect to FIGS.4A-4C may be used to select various functions. In step 826 previousfunction settings may be recalled. The function settings may be recalledfrom the application or the memory associated with the programmingdevice or by connecting to the helmet in step 822.

In step 830 various functions may be desired to be limited. A functioninterface may be displayed. The functional interface may changedepending on the user or type of user. For example, various age levelsof children may have different types of functions limited. For otheradult users other types of functions may be set.

In step 832 the user interface associated with the programming device isused to adjust or set the functional settings to form updated functionsettings. The updated functions settings are stored in step 834 at theapplication and or at the helmet memory. As indicated above a storebutton may be selected so that the settings are stored within theprogramming device and or the helmet or both.

Referring now to FIG. 9, a method for communicating the functionsettings to the vehicle is set forth. In step 900 it is determinedwhether the helmet is proximate to the vehicle. As mentioned above aproximity sensor may detect the proximity of the helmet to the vehicle.The proximity may also be determined when a key is activated within theignition of the vehicle.

In the simplest form, step 902 may enable the starting of the vehiclewhen the helmet is proximate to the vehicle. The helmet communicates anidentifier to the vehicle controller. The identifier may identify thehelmet as a helmet to allow starting. The vehicle controller may alsoidentify the identifier as authorized. Therefore, unless thehelmet/identifier is authorized the vehicle will not start. That is,when a helmet without an identifier is not present, step 904 may disablethe vehicle from starting. Alternately, starting may be allowed but avery low top speed may be set to allow the vehicle to be moved. In step906 may display a warning that a helmet is not present and the vehiclewill not start unless a helmet is present. After step 900, step 912initiates communication between the helmet and vehicle functioncontroller 16. Function settings stored within the helmet may becommunicated to the vehicle by way of an RF interface, Bluetooth®, orsecure access interface.

In step 916 function settings may be stored within the vehicle. That is,the function settings from the helmet may be stored within the memory ofthe vehicle function controller 16.

In step 918 the function settings are communicated to the vehicle. Thecontroller illustrated in FIG. 6 may control various functions or thefunctions may be communicated through the controller area network 618 tovarious other controllers that control such functions as a powersteering unit, a ride height controller or the other types ofcontrollers or functions described above.

In step 920 the function settings may be displayed in the screen displayillustrated in FIG. 6.

In step 922 it is determined whether the function settings have beenadjusted or are operating outside the range. If the function settingsare operating outside the range or attempts to operate the vehicleoutside of the range step 924 limits the system to operate using thefunction settings to limit the operation of the vehicle. In step 922when the system is operating within the range the vehicle is operatedaccording to the function setting or according to the operation of thevehicle as long as the vehicle is being operated within the limits ofthe function setting.

Referring now to FIG. 10, a method for operating the vehicle whenmultiple helmets are detected. In step 1010 the system detects multiplehelmets. In step 1012 communication is initiated between the helmet andthe vehicle for all the helmets nearby. In step 1014 the functionsettings for each helmet are communicated to the vehicle controller. Instep 1016 the functions are adjusted to the most restrictive or thesafest function or functions. In step 1018 the vehicle is operated withthe most restrictive functions.

Referring now to FIG. 11, a method of initiating the pairing of a helmetto a vehicle is set forth. While the “helmet” and the “vehicle” aredescribed, the pairing is between a transceiver of the vehicle and atransceiver of the helmet. In step 1110, movement of the helmet isdetected at the controller of the helmet control system. Movement isdetected from a movement sensor that generates a movement signal. Instep 1110, if movement is not detected the system repeats at step 1110.In step 1110, if movement is detected in response to the movementsignal, step 1112 is performed. Step 1112 determines if the helmet isunpaired. When the helmet is not unpaired, meaning that the helmet ispaired, step 1110 is again performed. In step 1112, if the helmet isunpaired, step 1114 is performed. In step 1114, a pairing request signalis communicated from the transceiver of the vehicle. The pairing requestsignal may include such things as an identifier of the helmet. Othertypes of communication data may also be included such as a communicationfrequency, a key for communication, an encryption scheme or the like.After step 1114, step 1116 determines if the ignition of the vehicle isinitiated. As mentioned above, the ignition is initiated by such thingsas a lock cylinder being rotated or a button being pushed to start thevehicle when the vehicle is started and ignition signal is generated. Instep 1116, it is determined whether the ignition has been initiated. Ifthe ignition has not been initiated, step 1110 is again performed. Whenthe ignition has been initiated, step 1118 initiates the pairing timerwhich corresponds to a maximum time that the system is allowed toperform pairing. The pairing timer may be a countdown timer or may be alimit that is set for an amount of time that the vehicle will “look” fora pairing request signal. In step 1120, the receiver of the transceiverof the vehicle is monitored for a pairing request signal. When a pairingsignal is not received in step 1122, step 1124 determines whether thetime has been exceeded such as when a time exceeds a threshold. The timecorresponds to the timer initiation of step 1118. Steps 1120 and 1122are again repeated when the time threshold has not been exceeded.

Referring back to step 1122, when the pairing signal is received, step1126 generates a screen display at a user interface such as theconfirmation indicator 730 illustrated in FIG. 7. In step 1128, the usermay interface with the user interface and a confirmation signal may begenerated at the user interface in step 1128. After the confirmationsignal is generated at the user interface, it is communicated to thecontroller 610 of the vehicle. In step 1130, the helmet is paired to thevehicle. That is, as mentioned above, the helmet transceiver is able tocommunicate with the vehicle transceiver. Details of the pairing processare described in FIG. 12.

After step 1130, step 1132 allows communication signals to betransmitted between the helmet and the vehicle. After step 1124 andafter step 1132, the process ends in step 1134.

Referring now to FIG. 12, details of the pairing process are set forth.In step 1210, a first signal such as the pairing request signal iscommunicated from the helmet such as in response to a movement of thehelmet as described above. The first signal may have an identifier keyand communicate various parameters such as a frequency, a key, or othertype of encoding or encryption data. The first parameters allow thehelmet transceiver to communicate with the vehicle transceiver. In step1212, the first signal is received at the transceiver of the vehicle. Inparticular, the receiver portion of the transceiver receives the firstsignal and the parameters therein. The transceiver “looks” for thesignal as described in FIG. 11. In step 1214, a response signal isgenerated with a second communication signal parameter to the helmet.The second communication parameters may include an acknowledge signal,an enable signal and other parameters for intercommunicating between thevehicle and the helmet. Passwords or numerical keys may be exchangedwith the first communication signal and the second communication signal.Once the communication signals are exchanged, a communication system isestablished in step 1216. This is referred to as pairing which allowsthe vehicles to exchange signals. For example, the helmet maycommunicate presettings for the vehicle. The vehicle, may transmitvarious data from the vehicle to the helmet. In step 1218, the secondcommunication parameters are stored in the helmet. In step 1220, thefirst communication parameters are stored in the vehicle. In step 1222,various other types of signals are communicated between the helmet andthe vehicle. More specifically, various types of data signals may beexchanged between the transceiver of the helmet and the transceiver ofthe vehicle.

The foregoing description has been provided for purposes of illustrationand description. It is not intended to be exhaustive or to limit thedisclosure. Individual elements or features of a particular example aregenerally not limited to that particular example, but, where applicable,are interchangeable and can be used in a selected example, even if notspecifically shown or described. The same may also be varied in manyways. Such variations are not to be regarded as a departure from thedisclosure, and all such modifications are intended to be includedwithin the scope of the disclosure.

1-20. (canceled)
 21. A system comprising: a programming devicecomprising an application for programming vehicle function settings of avehicle, said programming device comprising a transmitter communicatingthe vehicle function settings of the vehicle; a vehicle receiverdisposed within the vehicle, said vehicle receiver receiving the vehiclefunction settings; a vehicle controller disposed within the vehicle; ahelmet generating a helmet movement signal in response to sensingmovement of the helmet, said helmet communicating a helmet identifier tothe vehicle controller through the receiver in response to the helmetmovement signal; and said vehicle controller controlling a vehiclefunction in response to the vehicle function settings.
 22. The system ofclaim 21 wherein the transmitter communicates using one of Bluetooth,Wi-Fi, short range or long range communications and cellularcommunications.
 23. The system as recited in claim 21 wherein thereceiver comprises a Bluetooth® receiver.
 24. The system of claim 21wherein the vehicle function settings limit operation of the vehicle inresponse to the identifier.
 25. The system of claim 21 wherein thevehicle function settings comprises disabling starting of the vehicle.26. The system as recited in claim 21 wherein the vehicle functionsettings further comprise at least one of a top speed setting, a radiovolume setting and a geographical setting.
 27. The system as recited inclaim 21 wherein the vehicle comprises a display displaying the vehiclefunction settings.
 28. The system as recited in claim 21 furthercomprising a proximity sensor generating a proximity signal, saidvehicle controller powering the vehicle receiver, in response to theproximity signal.
 29. The system as recited in claim 28 wherein theproximity sensor comprises a key press or a button press.
 30. The systemas recited in claim 21 wherein the programming device comprises a seconddisplay displaying a plurality of selectors for changing the vehiclefunction settings.
 31. The system as received in claim 30 wherein theplurality of selectors comprises at least one of a speed limit selector,and a radio volume selector, a ride height selector, a radio presetselector, a map setting selector and a steering effort selector.
 32. Thesystem as received in claim 21 wherein the programming device storesfunction settings in the helmet, said helmet stores the vehicle functionsettings therein and communicates the function settings to the vehiclereceiver.
 33. A method comprising: programming vehicle function settingsof a vehicle using a programming device; communicating the vehiclefunction settings of the vehicle using a transmitter of the programmingdevice; receiving the vehicle function settings at a vehicle receiverdisposed within the vehicle; generating a helmet movement signal at ahelmet in response to sensing movement of the helmet, communicating, bythe helmet, a helmet identifier to the vehicle controller through thereceiver in response to the helmet movement signal; and controlling avehicle function in response to the vehicle function settings.
 34. Themethod of claim 33 further comprising limiting an operation of thevehicle in response to the helmet identifier and the vehicle functionsettings.
 35. The method of claim 33 wherein controlling the vehiclecomprises disabling starting of the vehicle, based on the vehiclefunction settings.
 36. The method of claim 33 wherein controllingcomprises limiting at least one of a top speed setting, a radio volumesetting and a geographical setting.
 37. The method of claim 33 furthercomprising generating a proximity signal at a proximity sensor and,powering the vehicle receiver, in response to the proximity signal. 38.The method as recited in claim 37 wherein generating the proximitysignal comprises pressing a key or button.
 39. The method of claim 33wherein the programming device comprises a second display displaying aplurality of selectors for changing the vehicle function settings,wherein the plurality of selectors comprises at least one of a speedlimit selector, and a radio volume selector, a ride height selector, aradio preset selector, a map setting selector and a steering effortselector.
 40. The method of claim 33 further comprising storing functionsettings in the helmet, and communicating the function settings to thevehicle receiver.